Hi All, Recently we have migrated email services from exchange 2003 to 2007 in our organization.There is a problem poped out for a single user stating that Delivery has failed to these recipients or distribution lists: <Email Display Name> The recipient's mailbox is full and can't accept messages now. Microsoft Exchange will not try to redeliver this message for you. Please try resending this message later, or contact the recipient directly. Diagnostic information for administrators: Generating server: /O=org/OU=office/cn=Recipients/cn=user alias#MSEXCH:MSExchangeIS:/DC=com/DC=domain name:server name[522:0x000004D9:0x0000000D] #EX# ----------------------------------------------------------------------------------------------------------------------------- When i checked the recipient mailbox size it is much available to receive a new message (only 25 MB) whereas sender mailbox is full. Sender is receiving mail as recipient mail box is full Please advice me a corrective cource of action

Hi, It seems like the sender’s mailbox has exceeded the Prohibit Send Quota setting on the mailbox or on the mailbox database. For more information regarding the quota setting, you can refer to following article: Interpreting Status of Storage Quotas via Exchange Management Shell http://msexchangeteam.com/archive/2006/09/20/428965.aspx Regards from www.windowsadmin.info

If the above mentioned is the issue,then sender might have received the message like "your quota limit exceeds" This is totally different I would like to explain this issue further more so that you can help me out in this For Example, Sender:Raaj ; Recipient :Durai Raaj is sending mail to Durai with the message size is of 20 KB.Raaj receivies message from server stating that Durai's mailbox is full.Where as durai's mail box is only 25 MB and his quota limit is 100 MB. When i checked both mailboxes,Raaj's mailbox exceeded the quota limit Hope this clears

Hi Raajdurai, Now only I have noticed the exact situation from your second reply. I hope any of the following command can help to resolve the issue The following example shows how to set the mailbox size at which users associated with mailboxes in this mailbox database can no longer send messages. This attribute applies to all mailboxes in this mailbox database that do not have their own prohibit send quota attributes set. The limit value set must be either an integer or "unlimited." Set-MailboxDatabase "Mailbox Database Name" -ProhibitSendQuota 2097152 The following example shows how to set the mailbox size at which the user associated with this mailbox can no longer send or receive messages. This attribute applies to all mailboxes in this mailbox database that do not have their own prohibit send receive quota attributes set. You must specify either an integer or "unlimited." Set-MailboxDatabase "Mailbox Database Name" -ProhibitSendReceiveQuota 2411520 Regards from www.windowsadmin.info

Hi, When a user with a mailbox send limit exceeded tries to send an email ,he receives and NDR informing that the recipient mailbox was exceeded instead of the send being blocked; It is a know issue. It has been correct by sp2 for Exchange 2007. You'd better to apply sp2 for Exchange server 2007. For this issue, I think we need to check the send limit on the sender as follow ManU said to modify the prohibitsendquota value. Set-MailboxDatabase http://technet.microsoft.com/en-us/library/bb123971(EXCHG.80).aspx Interpreting Status of Storage Quotas via Exchange Management Shell http://msexchangeteam.com/archive/2006/09/20/428965.aspx Regards, Xiu

I just found this thread by searching for "The recipient's mailbox is full and can't accept messages now. Microsoft Exchange will not try to redeliver this message for you. Please try resending this message later, or contact the recipient directly". I have the exact same scenario where the message originator had the mailbox over the size limit, however the Underliverable message came back as if the target's mailbox was over the size limit. That is the string I searched for that led me here. We are running Exchange 2007 SP2 RU4 accross the board. Is it possible this bug was re-introduced after SP2?